home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 1
/
Cream of the Crop 1.iso
/
UTILITY
/
DOSIMP12.ARJ
/
SIMPLY1.HYP
< prev
next >
Wrap
Text File
|
1992-01-16
|
60KB
|
1,213 lines
|Tby Kari M. Jackson|T
|TDDDDDD OOOO SSSS |T
|TDD DD OO OO SS SS|T
|TDD DD OO OO SS |T
|TDD DD OO OO SS |T
|TDD DD OO OO SSS |T
|TDD DD OO OO SS |T
|TDD DD OO OO SS|T
|TDD DD OO OO SS SS |T
|TDDDDDD OOOO SSSS |T
(Disk) (Operating) (System)
|TSimply Said,|T
|TSimply Done,|T
|TSIMPLY EASY!|T
|TVersion 1.2|T |T(c)1991|T
<page down> for instructions and menu
INSTRUCTIONS |nFOR|n NAVIGATING THIS BOOK
Hotspots--highlighted words which take you to their target when you put
your cursor on them and hit <Enter>.
Targets--the part of the text that explains a word in a hotspot.
<PageUp> and <PageDown> keys--take you through the book a page at a time.
<Arrow> keys--move from hotspot to hotspot on the same page.
<Letter> keys--move to a hotspot on the page starting with that letter.
<Enter> key--takes you to the target of whatever hotspot you're on.
<Ctrl-Enter> keystroke--returns you to where you last hit <Enter>.
<Home> key--takes you to the point where you entered the |ncurrent|n file.
<Ctrl-PageUp> keystroke--takes you to the first page of the |ncurrent|n file.
<Ctrl-Home> keystroke--takes you to the title page of the book, where you
are only two <PageDown>s away from the Main Menu.
<Esc> key--exits the book.
<Ctrl-/> keystroke--exits the book and if you're using the TSR version of
the Hypertext reader, it saves your spot so that the next time you enter
the book, you'll be at that spot rather than at the title page.
WORDS ON THE MENU WHICH HAVE » NEXT TO THEM ARE THE FIRST ONES YOU SHOULD
READ. WORDS WITH φ ARE DANGEROUS--DON'T USE THEM UNTIL YOU'VE READ THEM!
<page down> for menu
-=|sWhat Is DOS?|s=- -=|sAbout This Program|s=-
╔═════════╗
φ APPEND |sDATE|s/|sTIME|s φ FDISK |sMKDIR|s/MD » SHARE ║ DOS 5.0 ║
φ ASSIGN φ DEBUG FILES MODE » SHELL ╚═════════╝
ATTRIB |sDEL|s/|sERASE|s FIND MORE SHIFT DEVICEHIGH
» BACKUP DEVIC|1E FOR NLSFUNC SORT DO|1S
φ BREAK DIR FORMAT » PATH STACKS » DOSKEY
BUFFERS DISKCOMP GOTO PAUSE φ SUBST EDIT
CALL DISKCOPY GRAFTABL PRINT SWITCHAR EMM386
CHCP DOSSHELL GRAPHICS PROMPT SWITCHES EXPAND
|sCHDIR|s/CD DRIVPARM GWBASIC φ RECOVER SY|1S HELP
» CHKDSK ECHO IF REM TREE LOADFIX
CLS EDLIN INSTALL |sRENAME|s/REN TRUENAME |sLOADHIGH|s/LH
COMMAN|1D EXE2BIN φ JOIN REPLACE TYPE MIRROR
COMP EXIT KEYB RESTORE VER QBASIC
COPY φ FASTOPEN LABEL |sRMDIR|s/RD φ VERIFY SETVER
COUNTRY FC LASTDRIVE SELECT VOL UNDELETE
φ CTTY FCBS MEM SET XCOPY φ UNFORMAT
<page down> for more subjects
» Memory
══════ » Disks
Conventional Special Files ═════
EMS ═════════════ Bad Sector
Expanded » ". and .." External » Boo|1t Disk
Extended *.* FAT Cluster
Hig|1h ANSI.SYS Hidden Floppy
HMA ASCII HIMEM.SYS Fragmented
Kernel » AUTOEXEC.BAT IBMBIO.COM Logical Drives
LIM » Batch IBMDOS.COM Low-Level
Protected Mode » COMMAND.COM Internal Media
RAM » CONFIG.SYS IO.SYS Optimizer
Real Mode Device Driver MSDOS.SYS » Park
Reserved » Directory Overlay Partition
ROM DRIVER.SYS RAMDRIVE.SYS RAMdisk
Shadow EGA.SYS SMARTDRV.SYS Sector
» TSR » Executable VDISK.SYS Slack Space
UMB Virtual Disk
Upper Volume
XMS <page down> for more subjects » Write-Protect
Software Distribution Error Messages » Device|1s
═════════════════════ ══════════════ ═══════
BBS Abort, Retry, Fail, Ignore AUX
Commercial Access Denied CLOCK$
Demo Bad Command or Filename COM1
Downloading Disk Full CON
Freeware File Creation Error LPT1
Public Domain Incorrect DOS Version NUL
» Shareware Insufficient Disk Space PRN
Invalid COMMAND.COM
Environment Invalid Drive Specification Precautions
═══════════ Non System Disk ═══════════
COMSPEC Packed File Corrupt » Cleaning
DIRCMD Sector Not Found » Magnetism
TEMP Track 0 Bad » Power
<page down> for more subjects
» A|1: Filter
Archive Handles
CPU » Attributes » Keyboard
═══ Numbering Systems » Boot Macros
8088 ═════════════════ Bytes NOT
XT Binary » C|1: » Parameters
286 Decimal Cache Parent
AT Hexadecimal Checksum Piping
386 Code Page Queue
BIOS φ Concatenation Reboot
» CMOS Current » Redirection
Interrupt Default Replaceable
POST » Editing Keys Root
Setup ERRORLEVEL » Shelling Out
EXIST Spooler
» Wildcards
-=|sTrademarks|s=-
|TAbout This Program|T
This "book" is dedicated to all the Computer Club members on the Prodigy
Online Service who always made me feel so good, by thanking me so heart-
ily for my help with their DOS problems. (You know who you are!) This
is my way of saying "You're welcome!" And to all those who suggested,
told, or begged me to write this, I hope it meets your expectations.
The text is all my own, of course, but the Hypertext reader you're using
to read this, and the Hypertext compiler I used to put it together, is a
piece of shareware written by Derek Gitelson of Sansaska Systems.
It's really fun to write Hypertext. Much more fun than just typing on a
word processor, because from the results, you can almost pretend that
you're actually "programming" or something. Really, if you look at this
file with a browser, you'll see that it's just plain text with a few con-
trol characters like ||t and ||n to tell the compiler which words are to be
used as "targets", and which are to be highlighted as "hotspots" which
take you to the target when you put your cursor on them and hit <Enter>.
<page down> for more About This Program
Well, once you have the text written and the control characters inserted,
the compiler takes care of all the hard work, doing all the indexing and
everything. Then all you have to do is proofread it about six hundred
times. Except for that part, it's fun.
So if you'd like to do a little Hypertext writing yourself, may I recom-
mend Mr. Gitelson's program, HeLPyoURSeLF. You can probably find it on
your local BBS, or you can fill out his registration form that I've in-
cluded in the documentation for this program, and send the form along
with $20 + $2.50 shipping and handling, to Mr. Gitelson, and he'll send
you a registered copy of his program. Or, you can just send it to me
along with your order for a registered copy of my "book", and I'll for-
ward it to him immediately.
Special thanks to Derek Gitelson for allowing me to license his Hypertext
program, to Cheryl Palardy for suggesting the title that I finally decid-
ed on, and to my "beta testers" (proofreaders), Chris Alumbaugh of Rock-
ford IL, Roy Patton of Dallas TX, Wayne Strang of Torrance CA, and my
mentor, Stan MacDonald of Omaha NE.
<page down> for more About This Program
In case you've somehow lost the README.BAT file that came with this pro-
gram, here's how to register. For this "book", send $25 + $4 for ship-
ping, and $1.63 for 6.5% sales tax if you're in Nebraska, to Kari Jack-
son, 3201 Monroe, Omaha NE, 68107-4048 and tell me what size and density
of disk you need, and whether you want the printable text version as well
as the normal Hypertext one.
If you want to order the Hypertext compiler, send $20 + $2.50 for ship-
ping, and $1.40 for 7% sales tax if you're in California, to Sansaska
Systems, 3311 Concord Blvd, Concord CA, 94519 and of course let him know
also what size disk you need. These prices are |ncurrent|n as of 01/92 but
are subject to change in the future. Mr. Gitelson is offering his pro-
gram at $5 off the normal price, to purchasers of both this "book" and
his Hypertext program, so be sure to let him know that you're ordering it
through me so that he knows why you're only sending $20 instead of $25.
<page down> for |nTrademarks|n
|TTrademarks|T
The following products are |ntrademarks|n, registered |ntrademarks|n, or copy-
rights of their respective companies:
4DOS--JP Software
8086, 8088, 286, 386, 486, 586--Intel
ANSI--American National Standards Institute
ASK, CAPSLOCK, HIDE, PC/Computing--Ziff-Davis Publishing
BROWSE, KEY-FAKE, PC Magazine--Ziff-Davis Publishing
COMPAQ--COMPAQ Computer
CompuServe--H&R Block
EMS, |sLIM|s--Lotus Development, Intel, and Microsoft
Epson--Epson America
EXPLOSIV--Reidar Gresseth and Chris Hook
GW-BASIC, MS-DOS--Microsoft
Hayes--Hayes Microcomputer Products
HeLPyoURSeLF--Sansaska Systems
HISTORY--Bryan Higgins
Kaypro--Kaypro
<page down> for more Trademarks
Manifest, QRAM--Quarterdeck Office Systems
MARK and RELEASE--TurboPower Software
NANSI--Daniel Kegel
Norton Utilities--Peter Norton Computing
PC, XT, AT, PC-DOS, IBM-DOS--International Business Machines
PC Tools--Central Point Software
PKZIP, PKUNZIP, PKZIPFIX--PKWARE
Prodigy--Prodigy Services
QEMM, VIDRAM--Quarterdeck Office Systems
SpinRite--Gibson Research
TIMEPARK--Alpha Computer Service
UNIX--AT&T Bell Laboratories
ViruScan--McAfee Associates
WordStar--MicroPro International
|sXMS|s--Lotus Development, Intel, Microsoft, and AST Research
Zenith--Zenith Electronics
ALIAS, CED, and any other names, are from various other share-
ware/|sfreeware|s/|spublic domain|s/|scommercial|s software authors.
<page down> for more Trademarks
If I've left anyone out, it certainly was not intentional, and I hope you
will forgive me, as well as letting me know so that I can correct the
problem in my next release!
<page down> for |nWhat Is DOS?|n
|TWhat Is DOS?|T
DOS stands for Disk Operating System. It's a bunch of files on a disk,
that tell the computer how to deal with such things as files, programs,
disks, and directories. The main parts of DOS, meaning the Hidden files,
along with the file COMMAND.COM, have to be loaded into the computer's
memory each time you turn on the power, or else the computer won't know
how to do anything. As long as you have a proper boo|1t disk, this loading
of DOS into memory is handled for you automatically by a tiny software
program which is permanently stored in the computer on a ROM chip. Until
DOS is loaded into memory, the computer has no idea how to do anything,
other than load DOS into memory. Computers are totally stupid until a
software program tells them what to do. Well DOS is the main software
program that the computer needs, in order to know how to deal with any
other software program.
Well that's what DOS is as far as the computer is concerned. But what is
DOS to you? DOS is what lets you organize your files, and optimize your
system to make it run the way you want it to run.
<page down> for more What Is DOS?
A file is just the method that DOS uses to store information on a disk.
All of your programs are made up of files, and all the data you enter in-
to your programs is stored as files. If you write a letter using your
word processor, and you save that letter to disk, you have to give it a
filename, and then your word processor will tell DOS to write your letter
to the disk, under that filename.
You see, DOS acts as an interpreter between you and the computer, and be-
tween your word processor or other applications and the computer. DOS
will let you or your applications create files, move files, copy files,
rename files, organize files into a directory, and all sorts of great
things like that. Most of the DOS commands are even pretty straightfor-
ward as to what they are named. For example, the command you use to copy
a file to a different location is COPY. The command to erase a file from
your disk is ERASE. In order to move a file, you use those two commands
together. First you copy the file to a different location, and then you
erase the original. DOS doesn't give us a separate MOVE command, so that
in case something goes wrong with the COPY command, the original file
won't automatically get deleted. If you receive an error message from
<page down> for more What Is DOS?
the COPY command, you can figure out what the problem was, correct the
problem, and make a good copy of the file, before you erase the original.
Now you have to be careful and always take a look at what you've typed,
before you hit the <Enter> key, because DOS will do what you say, not
what you mean. There's a standing joke in the computer world about how
someone should put a DWIM (Do What I Mean) key onto a keyboard. There's
another joke about an UNDO key. But those keys don't exist. DOS does
exactly what you tell it to do, even if that wasn't what you meant to
tell it, and in most cases you can't undo it after it's been done.
One thing that causes a lot of confusion among new computer users is mix-
ing up the / and \ keys. They have separate uses, and if you hit / when
DOS wants to see \, that won't work. The \ (backslash) is for separating
directory names, and the / (forward slash) is for switch parameters.
DOS lets you customize your system to your own taste, by using the files
called CONFIG.SYS and AUTOEXEC.BAT. These are just plain ASCII text
files that contain commands that you want to have performed every time
<page down> for more What Is DOS?
you turn on the computer. There are tons of commands that you can use in
these two files, to make the computer run the way you want it to run.
You can also use DOSKEY macros, or batch files, to make the computer do
things that you want it to do, for which separate commands don't already
exist. You use EDLIN or COPY CON or any editor to create these files.
There are just so many things that you can do with DOS, that you can't do
if you don't know how to work with DOS. Lots of people think that it's
not necessary to know anything about DOS in order to make a computer go.
Well, that's true, up to a point, but when something goes wrong, those
people have to call someone else to fix it. People who know DOS don't
have to do that. In fact, people who know DOS are going to have fewer
things go wrong in the first place, because they know what to do in order
to keep things from going wrong. Well, that's the whole point of this
"book", is that knowing how to use DOS is going to make your computer
life a whole lot easier, more enjoyable, and more productive. So read
on!
<page down> for The |nUNDELETE|n Command
The |tUNDELETE|t Command
This command is new to DOS version 5.0, but it's been around for a while.
Microsoft licensed it from Central Point Software, the publishers of PC
Tools. It does just what its name implies.
First of all, the DEL and ERASE commands have never deleted any of the
data in your files. All they do is erase the FAT entry, and the first
letter of the filename in the directory entry. They don't even touch the
file. Well the directory entry tells the location of the beginning of
the file, so all that's missing after a file has been deleted, is the
first letter of the filename, right? That should be really easy to fix.
Wrong. Because the directory entry tells the location of only the begin-
ning of the file, not all the other little pieces of a file. That's what
the FAT does. It tells the location of all the other parts of the file
after the first. This is especially important for fragmented files!
Well, if you've been running the MIRROR program with its deletion track-
ing TSR, then it's been saving a record of the FAT and directory entries
<page down> for more UNDELETE
for every file you've deleted. So as long as neither you, nor DOS, nor
any other program has written any data, including the temp files caused
by the DOSSHELL or any redirection operations involving the || symbol, to
the spot on the disk where that file was, then the |nUNDELETE|n command can
easily, immediately, and perfectly restore any file you delete.
Even if you weren't running |sMIRROR|s's delete tracker, as long as no data
has been written on top of the deleted file, the |nUNDELETE|n command has a
chance of being able to work. As long as the file was not fragmented, it
will be able to restore everything except the first letter of the file-
name. But if the file was fragmented, you're in trouble. If the file in
question is on a floppy disk, make a DISKCOPY of it and see what the UN-
DELETE command can do for you, but only on the copy, not the original.
If it doesn't work, you still have the original so you can take it to
someone who knows more about manual undeletion than you do.
But if you have created any new files in that directory, since you delet-
ed the file, then that deleted file's directory entry has most likely
been reused for the new file, and there's no way you'll get the deleted
<page down> for more UNDELETE
file back then, unless you were running |sMIRROR|s's delete tracking TSR.
And remember that just because you haven't created any new files, doesn't
mean that DOS hasn't, or that your applications haven't. Temp files are
created and deleted all the time, and you usually aren't aware of it. So
the longer it's been since the file was deleted, the lower the chances
that it can be undeleted.
Think long and hard whenever you're about to use the RMDIR command, be-
cause the |nUNDELETE|n command cannot bring back a directory, or any files
that were in a directory after it's been |sRMDIR|sed. If the directory is a
branch right off the root directory, then the UNFORMAT command might be
able to get it back, and then you could use the |nUNDELETE|n command to re-
trieve the files that were in that directory. But it's not a good idea
to go around using the UNFORMAT command just for one directory. It could
do more harm than good.
Here's the syntax for this command:
|nUNDELETE|n D:\DIR\FILENAME.EXT /ALL /DOS /DT /LIST
If you leave out the file specification there, then the command will un-
<page down> for more UNDELETE
delete all the deleted files in the current directory.
The /LIST switch doesn't |nundelete|n any files. It just shows you which
files are available for undeletion, depending on whether you specify the
/DOS or /DT switch with the /L one.
The /ALL switch just goes right ahead and undeletes all the files that
there are to be undeleted, without asking for permission or anything. If
there is no delete tracking file to help, it will put a # sign in place
of the first character in each filename, and you can use the RENAME com-
mand to give the files back their real names.
The /DOS switch tells |nUNDELETE|n to ignore any delete tracking file and
just do what it can from the information in the deleted file's directory
entry.
The /DT switch undeletes only the files that have information stored for
them in the deletion tracking file.
<page down> for more UNDELETE
If you don't specify any of these switches, the |nUNDELETE|n command will use
the delete tracker file if it exists, otherwise it will try the DOS meth-
od with just the directory entry to go on.
<page down> for The |nUNFORMAT|n Command
The |tUNFORMAT|t Command
This command is new to DOS version 5.0, but it's been around for a while.
Microsoft licensed it from Central Point Software, the publishers of PC
Tools, where its name was REBUILD. It does just what its name implies.
In order for the |nUNFORMAT|n command to work, the disk it's being used on
needs to have been formatted by the DOS version 5.0 FORMAT command, and
without the /U switch. Because this new safe FORMAT command runs MIRROR
on the disk before it formats, to save a copy of the root directory and
FAT in the |nMIRROR|n.FIL file. (You won't need to have the |nMIRROR|n.COM file
available though, because the applicable parts of |sMIRROR|s's code are in-
side the |nFORMAT|n.COM file.) You won't be able to see that |nMIRROR|n.FIL file
on the disk, but unless you used the /U switch with the FORMAT command,
and unless you formatted the disk to a different capacity than it was or-
iginally formatted at, then it will be there. And the |nUNFORMAT|n command
will be able to use that little file to put the disk back to exactly the
way it was before you accidentally formatted it. Even if you did use the
/U switch with the FORMAT command, if you have used the MIRROR command on
<page down> for more UNFORMAT
that disk very recently, there's a good chance that the |nUNFORMAT|n command
will be able to help you.
The |nUNFORMAT|n command can also undo the horrors caused by the RECOVER com-
mand when it's been used on a whole disk or directory instead of only on
one file at a time like the poor misunderstood RECOVER command is meant
to be used. Also, |nUNFORMAT|n can undo a DEL \*.* which means deletion of
all the files in the root directory. And finally, if you have ever used
the MIRROR /PARTN command and still have the floppy disk that information
was saved to, then |nUNFORMAT|n can restore the partition table on your hard
drive, which is what needs to be done if you suddenly start receiving the
message "|tInvalid drive specification|t" for no apparent reason.
Just be careful with the |nUNFORMAT|n command! Don't go using it at the drop
of a hat. It is there for the purpose of recovering from a major disas-
ter, not just for playing around with. It doesn't always work perfectly,
so if you use it on a small mistake you could end up in worse shape than
you already were in. However, if you make a huge mistake, the |nUNFORMAT|n
command will leave you better off than you were even if it isn't able to
<page down> for more UNFORMAT
completely recover everything.
And don't dilly-dally around, between the time you make the horrible mis-
take and the time you get busy and decide to use |nUNFORMAT|n. If it's going
to be done, it needs to be done right away. Anything you do between the
mistake and the |nUNFORMAT|n could overwrite the data that you're hoping to
recover. And data that has had more data written on top of it can never
be recovered. Don't forget that an awful lot of DOS operations, like any
use of the || symbol or the DOSSHELL for example, writes temporary files
to the disk that you might not be aware of. Just because you have not
personally written anything to the disk since the mistake, doesn't mean
that DOS hasn't done so. The longer you wait before using |nUNFORMAT|n, the
greater the chance that the data will be overwritten before you can re-
cover it.
Here's the syntax for this command:
|nUNFORMAT|n D: /J /L /P /PARTN /TEST
where D: is, of course, the drive which holds the disk you want to fix.
<page down> for more UNFORMAT
The /J switch just tells |nUNFORMAT|n to check to see whether there are any
|nMIRROR|n.FIL and |nMIRROR|n.BAK files on the disk, and that they don't disagree
with the system information. You don't use any other switches along with
this one! When it's done, then you redo the |nUNFORMAT|n command with some
other switches instead of this one. The |nUNFORMAT|n /J command doesn't fix
anything, or write anything to the disk.
The /L switch does not use the MIRROR files to help rebuild the drive in-
formation. It just does its best with what's left of the directory.
The /P switch makes |nUNFORMAT|n send all the data that would normally go to
the screen, to the LPT1 printer port instead. You don't need this at all
if you have MIRROR files on the disk; only if you're using the /L switch.
The /PARTN switch is what makes |nUNFORMAT|n restore the partition table that
you had saved to a floppy disk ages ago with the MIRROR /PARTN command.
You don't use any other switches along with this switch except maybe the
/L switch which, when used with /PARTN, displays the partition table that
it's restoring. When |nUNFORMAT|n /PARTN is done, you will have to reboot
<page down> for more UNFORMAT
from a floppy disk and then use |nUNFORMAT|n to restore your directory and
FAT.
The /TEST switch causes the |nUNFORMAT|n command to just pretend like it's
recovering your disk, and it just shows you what it would be doing if you
had not used this switch, so that you can decide whether unformatting is
a good idea or not. The |nUNFORMAT|n /TEST command does not change anything
on the disk. This is only relevant if you haven't been using the MIRROR
command, or if you |sreboot|sed twice since the damage occurred, or if you
|sreboot|sed once and ran the FORMAT command once, so that both of your MIR-
ROR files are trash as well.
As long as a disk was not formatted with the /U switch, then |nUNFORMAT|n can
put it back to the way it was just before it was formatted. If the /U
switch was used with the FORMAT command, but if MIRROR had also been used
on that disk before, then |nUNFORMAT|n still has a chance, though not a great
one. And if it does anything in this case, it'll be putting things back
to the way they were at the time you last used the MIRROR command, so any
new files you have created since then will be lost, and any files you've
<page down> for more UNFORMAT
edited since then may also be lost.
If you delete all the files in your root directory, don't use |nUNFORMAT|n to
get them back unless you already tried UNDELETE and that didn't work.
If you use the |nUNFORMAT|n command without the /L switch, the MIRROR file
will be used to help reconstruct the data. First |nUNFORMAT|n will show you
the date and time of the two MIRROR files (if the /1 switch was used with
the MIRROR command, or if MIRROR has only been used once on that disk,
there will only be one file from which to choose) and ask if you want to
use the Latest one or the Previous one. If you have |sreboot|sed the compu-
ter with the MIRROR command in your AUTOEXEC.BAT file, or if you have
formatted a corrupted disk, or in any way used the MIRROR command since
the disaster happened, say P. Otherwise, say L. If it's on a floppy,
it's a really good idea to make two |sDISKCOPY|ss of the disk and try one
method on each of them; the Latest MIRROR file, the Previous MIRROR file,
and the |nUNFORMAT|n /L method. That way you have the greatest chance of re-
covering the data, even if you make the wrong decision as to which method
to use, because you have chosen all methods. It's too bad you can't use
<page down> for more UNFORMAT
DISKCOPY with a hard disk so that you could do the same thing.
If the disaster from which you want to recover was caused by something
other than DOS version 5's safe FORMAT command, and you've never used the
MIRROR command on that disk, or if the MIRROR file on the disk is very
old, or if the MIRROR file was created or updated after the disaster hap-
pened, then you'll need to try the |nUNFORMAT|n /L command. This method will
try to recover whatever it can from the directory entries on the disk.
You will definitely want to only use this command on a DISKCOPY of the
original disaster-disk. It may or may not help. If you do it on a copy
of the disk, then if it doesn't work you still have the original, and
maybe some utility package such as the Norton Utilities might be able to
do a better job of recovery. But if you try |nUNFORMAT|n on the only copy of
the disaster-disk, and it doesn't work, then it's too late for Norton to
be able to help.
If |nUNFORMAT|n /L finds a file that is fragmented, it will ask you whether
it should truncate the file (cut it off at the end of the last contigu-
ous |scluster|s) or delete it (so that you can try to manually undelete it
<page down> for more UNFORMAT
with a utility such as PC Tools or the Norton Utilities). Unless you
know an awful lot about manual undeletion, you won't be able to do any-
thing with it so go ahead and say Truncate so that at least you get part
of the file back. Of course this only applies to data files. Executable
files aren't a bit useful if they've been truncated!
<page down> for The |nXCOPY|n Command
The |tXCOPY|t Command
Oh, what a useful command, if you have DOS version 3.2 or higher! The
COPY command reads one file from the source, writes it to the target,
goes back to the source to read the next file, etc. But |nXCOPY|n reads as
many of the source files as can fit into the available RAM, writes them
to the target, and then goes back to get a bunch more from the source.
It's so much faster! And it also has a whole bunch of switches that can
make it do all sorts of things! (It can't copy Hidden files, though.)
Well, here is XCOPY's syntax:
|nXCOPY|n D:\DIR\FILENAME.EXT D:\DIR\ /A /D:|nDATE|n /E /M /P /S /V /W
where D:\DIR\FILENAME.EXT is the files you want to copy, and it can use
wildcards of course, or if you want to copy all the files in that direc-
tory, you can just say D:\DIR instead. The second D:\DIR\ is the drive
and directory you want to copy the files to. If you leave that part out,
|nXCOPY|n will bring the source files to the current directory. If D:\DIR\
doesn't exist, |nXCOPY|n will create it, but if you don't include that last
backslash, |nXCOPY|n will ask you whether you want D:\DIR to be a file or a
<page down> for more XCOPY
directory. If you're copying more than one file, then of course you want
D:\DIR to be a directory, rather than a file.
The /A switch tells |nXCOPY|n to only copy the files that have their Archive
attributes turned on. That means files that have been changed or created
since the last time a program that resets the A attribute was used. (All
BACKUP programs reset the A attribute when they handle files.) But when
the /A switch is used, |nXCOPY|n leaves that A attribute turned on when it's
done.
The /D:|nDATE|n switch tells |nXCOPY|n to only copy the files that were last up-
dated on or after |nDATE|n. For example |nXCOPY|n C:\SIMPLY A:\ /D:07-05-91 will
only copy files whose date in the directory listing is 7/5/91 or later.
The /E switch can only be used if the /S switch is used too, and it tells
|nXCOPY|n to create directories on the target disk just as they exist on the
source disk, even if there are no files in that directory on the source.
The /M switch is just like that /A switch, except that when the /M is
<page down> for more XCOPY
used, |nXCOPY|n turns off the A attribute for each file it copies! Oh, how
useful this is! Of course it's great for an alternative to the BACKUP
command, but it has an even better use. Have you ever tried to copy a
bunch of files to floppy, and there wasn't enough room on the floppy for
all the files, and the COPY or |nXCOPY|n command just stopped dead in its
tracks and said "|tInsufficient disk space|t"? Then you had to see which
files did make it to the floppy, and copy each of the rest of the files
separately. Didn't you just hate that? Well you never have to do it
again. Here's what you want to do. First, look and see which files al-
ready have their A attribute set. You need to know this, so that you can
put them back the same way when this is done, so that your backup program
will know which files need to be backed up. The command ATTRIB *.* /S
will show you all the files in the current directory and its subdirector-
ies, and there will be an A to the left of each file that has an A at-
tribute. (If you have DOS version 5, then the DIR command with the /A
switch will do this for you even easier. Just use DIR /AA to see the
files that have an A, or do DIR /A-A to see the ones that don't.) Now
keep track of the results of that command, for later. Step two is to
give A attributes to all the files you want to copy, and take A attrib-
<page down> for more XCOPY
utes away from files that you don't want to copy. Use the ATTRIB command
to do that. Step three is to issue the |nXCOPY|n command, with the /M switch
(and /S and /E if you want) and |nXCOPY|n will copy all the files that have A
attributes, and reset the A attribute for each file that it copies. Now
when the disk is full, |nXCOPY|n will stop and say "|sInsufficient disk space|s",
but that's ok. Just put in a fresh disk and use the <F3> key to issue
the exact same |nXCOPY|n command again. Now since the /M switch turned off
the A attribute for each file that it already copied, |nXCOPY|n will start
copying right where it left off. When |nXCOPY|n gives you back your DOS
prompt without saying "|sInsufficient disk space|s", then all your files are
copied. Now use the ATTRIB command to put the A attributes back the way
they were, and you're all set. This is not nearly as complicated as it
sounds from the description, so once you've tried it, next time you'll
probably remember the whole process without even reading this again. Of
course, if the whole reason you're doing this is for backup purposes, you
don't want to put the A attributes back the way they were when you're
done; you want them all to stay turned off.
The /P switch tells |nXCOPY|n to stop and ask you, before copying each file.
<page down> for more XCOPY
That's good for in case you want to copy almost all the files in a direc-
tory, or almost all the files that match a particular wildcard specifica-
tion, or almost all the files that have a later date than the |nDATE|n in the
/D switch, or almost all of whatever.
The /S switch makes |nXCOPY|n copy all the files in the specified directory,
and all the files in all of its subdirectories. If the subdirectories by
those names don't already exist as branches off the specified target dir-
ectory, then |nXCOPY|n will create them, as long as there are files inside
them. If you want |nXCOPY|n to create subdirectories that don't have any
files in them, then you want to use the /E switch along with the /S.
The /V switch makes |nXCOPY|n do the same worthless sort of verification that
the VERIFY command does. Don't bother. Use the COMP or FC command after
you make the copy instead of using this switch, if you want to verify it.
And the /W switch makes |nXCOPY|n wait for a keystroke before it starts copy-
ing. This is good if your |nXCOPY|n.EXE file is on a floppy disk that is not
the same disk you want to copy files from. You put the |nXCOPY|n.EXE disk in
<page down> for more XCOPY
the drive and issue the command including the /W switch, DOS reads the
|nXCOPY|n command code into memory, and then you can take out the |nXCOPY|n.EXE
disk and put in the source disk instead, and then |nXCOPY|n will start read-
ing the files you want to copy.
Of course, not even the wonderful |nXCOPY|n command can do anything with a
file that's too big to fit all on one floppy disk. For that you need the
BACKUP command, and then you'll need the RESTORE command from the same
DOS version to be able to read that backup file later.
<page down> for The |nEXE2BIN|n Command
The |TEXE2BIN|T Command
This is a command you're not going to need for quite some time, if ever.
If you don't already know what it is, then you may as well erase it from
your hard drive to save space. It converts .EXE files to .COM files, and
that is not anything you're ever going to want to do unless you're a
software developer. Don't even think about trying it out just for the
heck of it, because it won't work properly until the .EXE file has been
formatted in a certain way.
<page down> for The |nAUTOEXEC.BAT|n File
The |tAUTOEXEC.BAT|t File
The |nAUTOEXEC.BAT|n is a very special batch file. As long as it is located
in the root directory of the boo|1t disk, it will automatically be read by
COMMAND.COM every time you restart your system. (Exception: If there is
a SHELL statement in CONFIG.SYS, that does not have the /P switch, then
|nAUTOEXEC.BAT|n will not be run after all.) This file should contain any
commands that you want to have executed with each reboot.
If you load a TSR from |nAUTOEXEC.BAT|n, it should always come earlier in
the file than any PATH, SET, or PROMPT statements, if possible. This is
because every program, including |sTSR|ss, that runs under DOS gets its own
copy of the environment. The commands PATH, SET, and PROMPT put variable
strings into the environment. Therefore, if any of these commands are
used before the |sTSR|ss are loaded, the |sTSR|s's copy of the environment uses
more RAM than is needed.
The only trouble with placing the PATH statement near the end of AUTOEXEC
.BAT, though, is that DOS won't be able to find the command files for the
<page down> for more AUTOEXEC.BAT
commands issued from the |nAUTOEXEC.BAT|n unless the full file specification
for each command is listed on the command line of the batch file. For
example, to load a screen saver called EXPLOSIV into memory, the command
would usually be simply EXPLOSIV if the directory containing the EXPLOSIV
.COM file is listed on the PATH variable in the environment. But since
the PATH variable has not yet been set, the command must instead read as
follows:
C:\UTIL\EXPLOSIV
That is providing the EXPLOSIV.COM file is located in the \UTIL directory
of the C: drive. That way, DOS knows exactly where to find the command
file, even without the PATH variable. Sure, it's a little more typing to
do, but that's not a problem, since you only need to type this command
once, when you first create your |nAUTOEXEC.BAT|n file.
If there is no |nAUTOEXEC.BAT|n file located in the root directory of the
boo|1t disk, then DOS will |nprompt|n you for the date and time during each
|sboot|sup, just as if you did have an |nAUTOEXEC.BAT|n file that contained just
the DATE and TIME commands.
<page down> for more AUTOEXEC.BAT
One thing you do not want to do, if there are any |sTSR|ss loaded from your
|nAUTOEXEC.BAT|n, or if you're not sure, and there might possibly be any |sTSR|ss
in there, is execute this file from the DOS prompt by entering AUTOEXEC
as a command. The reason is that any |sTSR|ss that are listed in there have
already been loaded into memory, while you |sboot|sed the computer, and so
executing |nAUTOEXEC.BAT|n again without |sreboot|sing, would load a second copy
of those |sTSR|ss into memory. Well some |sTSR|ss realize when they're being
loaded a second time, and just won't go for it. That's fine. Other |sTSR|ss
just go ahead and load a second copy. That won't hurt anything, neces-
sarily, but it sure would be a waste of memory. But other |sTSR|ss, when you
try to load them twice, will lock up the whole computer. Don't execute
AUTOEXEC manually unless you're positive there are no |sTSR|ss in it. So if
you make a change to this file, and want to see how it works, just reboot
the computer. But have a boo|1t disk handy first, in case the change you
made was a mistake that locks up the system.
<page down> for The |nCLS|n Command
The |TCLS|T Command
This is the easiest DOS command there is. It CLears the Screen of any
data that might be on it, and puts the prompt and the cursor up in the
top left corner (called the "home" position). No parameters, no syntax
to learn, just |nCLS|n.
It's used mostly in a batch file, to clear up any unnecessary messages
that may have been left on the screen. It's also needed in many cases
if you're using the PROMPT command with ANSI.SYS ESC sequences to change
your screen colors. Because a new ANSI color changing command does not
affect the whole screen, only whatever gets put on the screen after the
command is issued. Also a lot of programs will reset your screen to some
other colors, so your chosen colors are gone when you exit from such an
application. In many cases a simple |nCLS|n command will bring them back.
If ANSI.SYS is installed, |nCLS|n works by sending ESC[2J to the screen.
This is the ANSI command that clears the screen. If for any reason you
can't get the |nCLS|n command to work, try installing ANSI.SYS with a DEVIC|1E
<page down> for more CLS
command in your CONFIG.SYS file.
One interesting tidbit of information, about the fact that DOS sends the
ANSI.SYS ESC sequence 2J to the screen in order to execute this command,
is that it's an easy way to get the ESC character into a file, for use
in your own ANSI ESC sequences. If you enter the command |nCLS|n > FILE.TXT
(see also |sRedirection|s) then instead of the screen clearing, a file will
be created that says ESC[2J only instead of ESC, it will actually contain
the ESC character, which looks like a little arrow. Now you can edit the
file to replace the 2J with whatever ANSI ESC command you want.
<page down> for The |nSETVER|n Command
The |TSETVER|T Command
This command is new to DOS version 5, and it is used to lie to programs
about what DOS version you are running. You see, many programs, as you
load them, the first thing they do is ask the operating system what ver-
sion it is. Well, programs that were written to accept an answer of any-
thing higher than X will run just fine under DOS 5. But some silly pro-
grammers told their program to accept an answer of version X through ver-
sion Y instead. And since a program like this was written before there
ever was a DOS version 5, it won't accept the answer of MS-DOS 5.00 at
all. The program is going to say "|tIncorrect DOS version|t", and refuse to
load into memory. Even if the program is perfectly compatible with ver-
sion 5, it won't run just because of a silly version number report. Well
Microsoft thought of a neat little way to get around this problem. First
call the publisher of the program that's giving you that "Incorrect DOS
version" error message, and ask them if the program is compatible with
DOS 5. If they say ok, then you can use the |nSETVER|n command to tell the
program that you're not running DOS 5.00 after all. First you have to
have |nSETVER|n.EXE loaded into memory as a device driver. To do that, if it
<page down> for more SETVER
hasn't already been done, just put this line into your CONFIG.SYS file:
|sDEVIC|1E|s=C:\DOS\SETVER.EXE (or |sDEVICEHIGH|s) and just like any other change
you make to the CONFIG.SYS file, you have to reboot to make it take ef-
fect. (And of course, that sample command assumes that your |nSETVER|n.EXE
file is located in the DOS directory of your C: drive.) Now, you just
issue a command like this:
|nSETVER|n C:\DOS WP.EXE 3.3
That is assuming that your |nSETVER|n.EXE file is located in your C:\DOS dir-
ectory and that the name of the program that's giving you trouble is WP
.EXE and 3.3 is a DOS version under which that program used to run just
fine. Now after you give that command, |nSETVER|n is going to display a
warning message about how Microsoft is not responsible for anything bad
that could happen if you use this command. But you already called the
publisher of the WP.EXE program, right? And they told you it was ok to
do this, so don't worry about that message. Now, you just have to reboot
one more time to make this version number change thing take effect, and
from then on, whenever you try to load that program into memory, DOS will
lie to it and tell it that you're running DOS version 3.3, and the WP.EXE
program will be perfectly happy.
<page down> for more SETVER
There are already some version-number lies automatically installed in the
|nSETVER|n.EXE program, the way it comes from Microsoft. To see what those
are, just type |nSETVER|n C:\DOS <Enter>. If you don't run any of those pro-
grams, you can remove their entries from the |nSETVER|n table, using the /D
switch of the |nSETVER|n command, like this:
|nSETVER|n C:\DOS WP.EXE /D /QUIET
The /DELETE or /D switch tells DOS to remove that particular entry from
the |nSETVER|n version table, and the /QUIET switch tells DOS to suppress the
display of the message that it usually displays when removing an entry
from the table. Removing unneeded entries from the table will cause the
version table to take up a little bit less memory next time you reboot.
Later, if you want to change the version number that you told |nSETVER|n to
report to a particular program, just issue the same |nSETVER|n command again
with the different version number. It won't waste any memory by using up
another entry in the table or anything. The new entry for that filename
will just replace the old one that's already in the table.
Now the |nSETVER|n command does make a permanent change to the version table
<page down> for more SETVER
that it keeps inside itself. So you only have to give the command once,
not every time you reboot or anything. |nSETVER|n will keep on lying to that
program every time you execute the program, forever and ever, as long as
you keep the |nSETVER|n.EXE DEVIC|1E command line in your CONFIG.SYS file.
If you're installing a new program that tells you "|sIncorrect DOS version|s"
and you fix it with |nSETVER|n and then it installs ok, try running the pro-
gram without |nSETVER|n and see what happens. It's possible that it's only
the installation program that checks for the DOS version. Maybe the pro-
gram itself never checks again because it just assumes that you're still
running the same DOS version you were running when you installed. If
that's the case, the program will work fine without |nSETVER|n and you won't
have to use that device driver all the time after all. It only takes up
a very tiny amount of memory, but hey, every bit counts.
If you are not using any of the programs that already have pre-installed
lies in the version table, and you're not planning to get any of them,
and you have tried all your programs under the new DOS, and none of them
need the |nSETVER|n lies, then you don't need to leave the |nSETVER|n.EXE device
<page down> for more SETVER
driver installed in your CONFIG.SYS file like the DOS 5.0 installation
program put it there. All it's doing is wasting memory if you don't run
any applications that need it.
The message "|sIncorrect DOS version|s" will also happen any time you try to
execute a DOS command from one version, after |sboot|sing from a different
DOS version. Most DOS commands are only supposed to run under their own
version, so if you've |sboot|sed with something else, the command is going to
quit on you. Find your copy of that command, that belongs to the DOS
version you |sboot|sed from, and use it instead of the copy from the wrong
version.
<page down> for What is the FAT?
What is the |TFAT|T?
Well, it's only the single most important part of a disk. |nFAT|n stands for
File Allocation Table. You know how a book has a table of contents and
an index? Well if your two-year-old nephew ripped the table of contents
and index out of a book, you would still be able to read the information
in the book. You'd just have to page through it and look at the chapter
titles and stuff. Well DOS isn't that smart. If DOS can't look in the
index and see the page number it wants to turn to, it won't even consider
thinking about trying to find any information. It just won't even try.
Well the root directory of a disk is like the table of contents of a
book. It tells DOS what the first page number (|scluster|s number) of each
chapter (file) is. But the |nFAT|n is even more important than that. Be-
cause files get fragmented. That means one fragment of a file gets stuck
over here on the disk, and another part of the file gets put over there
on the disk. It's not like a book, where all the pages of a chapter are
in the same place, one right after the other. Well DOS needs to look in
the index (FAT) of the book (disk) to see where all the other references
<page down> for more FAT
to that chapter (file) are at on the disk.
The directory entry for a particular file includes the cluster number for
the first cluster of that file. Now the |nFAT|n entry for that cluster tells
the number of the next cluster of the file. And the |nFAT|n entry for that
next cluster tells the number for the next cluster after that. And even-
tually one of the |nFAT|n entries will be the one that contains a special
character that says it's the last cluster of that file.
Well that's just about all you really need to know about the |nFAT|n. With-
out it, DOS won't even make an attempt to find your files on your disks.
The |nFAT|n is so important that DOS keeps two identical copies of it, just
to be on the safe side.
<page down> for The |nFASTOPEN|n Command
The |TFASTOPEN|T Command
I would not recommend this command to my worst enemy. It's sort of like
a tiny disk cache, only not nearly as well-behaved. Get yourself a disk
cache and get rid of this command.
Well, what it does is, it stores parts of the directory entries and FAT
that you have already accessed, in RAM which is fast, so that the next
time you need to access those same parts, you can get them from memory
instead of from the slow hard disk. Yes, that's exactly what a cache
does, only the cache does FAT and directory entries, and all other types
of disk information as well. And the cache does it less dangerously.
Well, I guess it would be pretty silly of me to tell you the syntax for
this command after I just got done telling you not to use it, huh? So I
guess I won't.
For beginning of File 2, see Batch
|tBatch|t|fSIMPLY2|f
|TCALL|T|fSIMPLY2|f
|TECHO|T|fSIMPLY2|f
|TERRORLEVEL|T|fSIMPLY2|f
|TEXIST|T|fSIMPLY2|f
|tfilter|t|fSIMPLY2|f
|TFIND|T|fSIMPLY2|f
|TFOR|T|fSIMPLY2|f
|TGOTO|T|fSIMPLY2|f
|TIF|T|fSIMPLY2|f
|TMORE|T|fSIMPLY2|f
|TNOT|T|fSIMPLY2|f
|TPAUSE|T|fSIMPLY2|f
|tpiping|t|fSIMPLY2|f
|tRedirection|t|fSIMPLY2|f
|TREM|T|fSIMPLY2|f
|TSHIFT|T|fSIMPLY2|f
|TSORT|T|fSIMPLY2|f
|TTEMP|T|fSIMPLY2|f
|T286|T|fSIMPLY3|f
|T386|T|fSIMPLY3|f
|T8088|T|fSIMPLY3|f
|TAT|T|fSIMPLY3|f
|TBIOS|T|fSIMPLY3|f
|tBytes|t|fSIMPLY3|f
|tCache|t|fSIMPLY3|f
|TCMOS|T|fSIMPLY3|f
|tConventional|t|fSIMPLY3|f
|TCPU|T|fSIMPLY3|f
|tDEVICEHIGH|t|fSIMPLY3|f
|TDO|1S|T|fSIMPLY3|f
|TEMM386|T|fSIMPLY3|f
|TEMS|T|fSIMPLY3|f
|tExpanded|t|fSIMPLY3|f
|teXtended|t|fSIMPLY3|f
|tHig|1h|t|fSIMPLY3|f
|tHIMEM.SYS|t|fSIMPLY3|f
|tHMA|t|fSIMPLY3|f
|tkernel|t|fSIMPLY3|f
|tLH|t|fSIMPLY3|f
|TLIM|T|fSIMPLY3|f
|tLOADFIX|t|fSIMPLY3|f
|tLOADHIGH|t|fSIMPLY3|f
|tmedia|t|fSIMPLY3|f
|tMemory|t|fSIMPLY3|f
|TMEM|T|fSIMPLY3|f
|TMODE|T|fSIMPLY3|f
|tPacked file corrupt|t|fSIMPLY3|f
|TPRINT|T|fSIMPLY3|f
|tProtected Mode|t|fSIMPLY3|f
|tqueue|t|fSIMPLY3|f
|tRAMdisk|t|fSIMPLY3|f
|tRAMDRIVE.SYS|t|fSIMPLY3|f
|TRAM|T|fSIMPLY3|f
|tReal Mode|t|fSIMPLY3|f
|TRECOVER|T|fSIMPLY3|f
|TREPLACE|T|fSIMPLY3|f
|treserved|t|fSIMPLY3|f
|TRESTORE|T|fSIMPLY3|f
|TROM|T|fSIMPLY3|f
|tSector not found|t|fSIMPLY3|f
|TSELECT|T|fSIMPLY3|f
|tsetup|t|fSIMPLY3|f
|tShadow|t|fSIMPLY3|f
|TSHARE|T|fSIMPLY3|f
|tSMARTDRV.SYS|t|fSIMPLY3|f
|tspooler|t|fSIMPLY3|f
|TSUBST|T|fSIMPLY3|f
|TTREE|T|fSIMPLY3|f
|tTSR|t|fSIMPLY3|f
|TUMB|T|fSIMPLY3|f
|tUpper|t|fSIMPLY3|f
|tVDISK.SYS|t|fSIMPLY3|f
|tVirtual Disk|t|fSIMPLY3|f
|TXMS|T|fSIMPLY3|f
|TXT|T|fSIMPLY3|f
|tANSI.SYS|t|fSIMPLY4|f
|tbad sector|t|fSIMPLY4|f
|TBREAK|T|fSIMPLY4|f
|TBUFFERS|T|fSIMPLY4|f
|TCOMSPEC|T|fSIMPLY4|f
|tCONFIG.SYS|t|fSIMPLY4|f
|tDevice Driver|t|fSIMPLY4|f
|TDEVIC|1E|T|fSIMPLY4|f
|tDRIVER.SYS|t|fSIMPLY4|f
|TDRIVPARM|T|fSIMPLY4|f
|tEnvironment|t|fSIMPLY4|f
|TEXPAND|T|fSIMPLY4|f
|TFCBS|T|fSIMPLY4|f
|TFDISK|T|fSIMPLY4|f
|TFILES|T|fSIMPLY4|f
|tfloppy|t|fSIMPLY4|f
|TFORMAT|T|fSIMPLY4|f
|TGRAPHICS|T|fSIMPLY4|f
|thandles|t|fSIMPLY4|f
|THELP|T|fSIMPLY4|f
|tIBMBIO.COM|t|fSIMPLY4|f
|tIBMDOS.COM|t|fSIMPLY4|f
|TINSTALL|T|fSIMPLY4|f
|tinterrupt|t|fSIMPLY4|f
|tInvalid COMMAND.COM|t|fSIMPLY4|f
|tIO.SYS|t|fSIMPLY4|f
|TJOIN|T|fSIMPLY4|f
|TLABEL|T|fSIMPLY4|f
|TLASTDRIVE|T|fSIMPLY4|f
|tLogical Drives|t|fSIMPLY4|f
|tmacros|t|fSIMPLY4|f
|TMIRROR|T|fSIMPLY4|f
|tMSDOS.SYS|t|fSIMPLY4|f
|tpartition|t|fSIMPLY4|f
|tPATH|t|fSIMPLY4|f
|tPROMPT|t|fSIMPLY4|f
|TSET|T|fSIMPLY4|f
|TSHELL|T|fSIMPLY4|f
|TSTACKS|T|fSIMPLY4|f
|TSWITCHAR|T|fSIMPLY4|f
|TSWITCHES|T|fSIMPLY4|f
|tTrack 0 bad|t|fSIMPLY4|f
|tvolume|t|fSIMPLY4|f
|T". and .."|T|fSIMPLY5|f
|TA|1:|T|fSIMPLY5|f
|TAUX|T|fSIMPLY5|f
|tBad command or filename|t|fSIMPLY5|f
|TC|1:|T|fSIMPLY5|f
|TCD|T|fSIMPLY5|f
|TCHCP|T|fSIMPLY5|f
|TCHDIR|T|fSIMPLY5|f
|tchecksum|t|fSIMPLY5|f
|TCLOCK$|T|fSIMPLY5|f
|tCode Page|t|fSIMPLY5|f
|TCOM1|T|fSIMPLY5|f
|tCOMMAND.COM|t|fSIMPLY5|f
|TCOMMAN|1D|T|fSIMPLY5|f
|tconcatenation|t|fSIMPLY5|f
|TCON|T|fSIMPLY5|f
|TCOPY|T|fSIMPLY5|f
|TCOUNTRY|T|fSIMPLY5|f
|TCTTY|T|fSIMPLY5|f
|tcurrent|t|fSIMPLY5|f
|TDATE|T|fSIMPLY5|f
|tdefault|t|fSIMPLY5|f
|TDEL|T|fSIMPLY5|f
|tDevice|1s|t|fSIMPLY5|f
|TDIRCMD|T|fSIMPLY5|f
|tDirectory|t|fSIMPLY5|f
|TDIR|T|fSIMPLY5|f
|TERASE|T|fSIMPLY5|f
|tExecutable|t|fSIMPLY5|f
|TEXIT|T|fSIMPLY5|f
|texternal|t|fSIMPLY5|f
|TGRAFTABL|T|fSIMPLY5|f
|tinternal|t|fSIMPLY5|f
|TKEYB|T|fSIMPLY5|f
|TLPT1|T|fSIMPLY5|f
|TMD|T|fSIMPLY5|f
|TMKDIR|T|fSIMPLY5|f
|TNLSFUNC|T|fSIMPLY5|f
|TNUL|T|fSIMPLY5|f
|tparent|t|fSIMPLY5|f
|TPRN|T|fSIMPLY5|f
|TRD|T|fSIMPLY5|f
|TRENAME|T|fSIMPLY5|f
|TREN|T|fSIMPLY5|f
|TRMDIR|T|fSIMPLY5|f
|troot|t|fSIMPLY5|f
|tShelling Out|t|fSIMPLY5|f
|TTIME|T|fSIMPLY5|f
|TTRUENAME|T|fSIMPLY5|f
|TTYPE|T|fSIMPLY5|f
|TVERIFY|T|fSIMPLY5|f
|TVER|T|fSIMPLY5|f
|TVOL|T|fSIMPLY5|f
|t*.*|t|fSIMPLY6|f
|tAbort, Retry, Fail, Ignore|t|fSIMPLY6|f
|tASCII|t|fSIMPLY6|f
|TBBS|T|fSIMPLY6|f
|tbinary|t|fSIMPLY6|f
|tBoot|t|fSIMPLY6|f
|tBoo|1t Disk|t|fSIMPLY6|f
|tCleaning|t|fSIMPLY6|f
|tcluster|t|fSIMPLY6|f
|tcommercial|t|fSIMPLY6|f
|tdecimal|t|fSIMPLY6|f
|tdemo|t|fSIMPLY6|f
|tdisk full|t|fSIMPLY6|f
|tDisks|t|fSIMPLY6|f
|tdownloading|t|fSIMPLY6|f
|tFile Creation Error|t|fSIMPLY6|f
|tfreeware|t|fSIMPLY6|f
|thexadecimal|t|fSIMPLY6|f
|tKeyboard|t|fSIMPLY6|f
|tLow-Level|t|fSIMPLY6|f
|tMagnetism|t|fSIMPLY6|f
|tNon system disk|t|fSIMPLY6|f
|tParameters|t|fSIMPLY6|f
|tPark|t|fSIMPLY6|f
|TPOST|T|fSIMPLY6|f
|tPower|t|fSIMPLY6|f
|tpublic domain|t|fSIMPLY6|f
|tReboot|t|fSIMPLY6|f
|tReplaceable|t|fSIMPLY6|f
|tsector|t|fSIMPLY6|f
|tShareware|t|fSIMPLY6|f
|tslack space|t|fSIMPLY6|f
|TSY|1S|T|fSIMPLY6|f
|tWildcards|t|fSIMPLY6|f
|tWrite-protect|t|fSIMPLY6|f
|tAccess denied|t|fSIMPLY7|f
|TAPPEND|T|fSIMPLY7|f
|tArchive|t|fSIMPLY7|f
|TASSIGN|T|fSIMPLY7|f
|tAttributes|t|fSIMPLY7|f
|TATTRIB|T|fSIMPLY7|f
|TBACKUP|T|fSIMPLY7|f
|TCHKDSK|T|fSIMPLY7|f
|TCOMP|T|fSIMPLY7|f
|TDEBUG|T|fSIMPLY7|f
|TDISKCOMP|T|fSIMPLY7|f
|TDISKCOPY|T|fSIMPLY7|f
|TDOSKEY|T|fSIMPLY7|f
|TDOSSHELL|T|fSIMPLY7|f
|tediting keys|t|fSIMPLY7|f
|TEDIT|T|fSIMPLY7|f
|TEDLIN|T|fSIMPLY7|f
|tEGA.SYS|t|fSIMPLY7|f
|TFC|T|fSIMPLY7|f
|tfragmented|t|fSIMPLY7|f
|TGWBASIC|T|fSIMPLY7|f
|tHidden|t|fSIMPLY7|f
|toptimizer|t|fSIMPLY7|f
|toverlay|t|fSIMPLY7|f
|TQBASIC|T|fSIMPLY7|f
